maintenance of board certification in ophthalmology; who cares?

Maintenance of Board Certification in Ophthalmology; Who Cares?

The issue of continuing education is vital for both physicians and patient safety, as it can protect physicians from the legal consequences of out-of-date management practices and protect patients from complications from out-of-date approaches. Following the pioneering establishment of the American Board of Ophthalmology in 1917, other organizations have established specialty board exams (1). T...

Engagement of groups in family medicine board maintenance of certification.

PURPOSE The American Board of Medical Specialties' Performance in Practice ("Part IV") portion of Maintenance of Certification (MOC) requirement provides an opportunity for practicing physicians to demonstrate quality improvement (QI) competence. However, specialty boards' certification of one physician at a time does not tap into the potential of collective effort. This article shares learning...

Who cares?

User Interfaces; Who Cares?

According to Michael Stonebraker’s experiences, if you select a group of well-known experts in database research and ask them to identify the domains where meeting use+ requirements is of primary importance and at the ‘same time more significant advances are needed and more research should be promoted, user interfaces comes out as number one in the list. This has been the case over the last dec...

Medication adherence: WHO cares?

The treatment of chronic illnesses commonly includes the long-term use of pharmacotherapy. Although these medications are effective in combating disease, their full benefits are often not realized because approximately 50% of patients do not take their medications as prescribed. Factors contributing to poor medication adherence are myriad and include those that are related to patients (eg, subo...

Security Holes . . . Who Cares?

We report on an observational study of user response following the OpenSSL remote buffer overflows of July 2002 and the worm that exploited it in September 2002. Immediately after the publication of the bug and its subsequent fix we identified a set of vulnerable servers. In the weeks that followed we regularly probed each server to determine whether its administrator had applied one of the rel...